1. **`kind`: `"ping"` with `webTestKind`: `"standard"`** — Incorrect for a **standard** test in Azure’s own ARM model. The [Bicep reference for `Microsoft.Insights/webtests`](https://learn.microsoft.com/en-us/azure/templates/microsoft.insights/webtests) uses `kind: 'standard'` and `properties.Kind: 'standard'` for standard tests. Illustrations now use `"kind": "standard"` throughout.
   (*Note:* There is [reported Azure CLI behavior](Azure/azure-cli#29135) where `kind` can look wrong vs `web-test-kind`; the samples are now aligned with the ARM/REST contract, not that quirk.)

2. **`locations` entries used `"location"`** — The API shape is **WebTestGeolocation** with **`Id`** (see REST examples). Sample outputs now use `"Id": "us-tx-sn1-azr"`.

3. **Limitations line on Playwright** — **`Playwright` is not a `WebTestKind`** on `Microsoft.Insights/webtests` (only `ping`, `multistep`, `standard` per the same REST/Bicep docs). Playwright-based availability is a **separate** pattern (e.g. custom workers + telemetry), not this resource type. The limitation was narrowed to **`multistep`** / XML sequence execution not being run locally.

## Other tweaks

- **Features:** Clarified linking via a `hidden-link` tag and pointed to the official Web Tests create/update examples.